Caching enhancements in WebSphere Commerce 6.0.0.1 and later | Cache replication
Cache replication
A large WebSphere Commerce environment utilizes WebSphere Application Server clustering to achieve scalability and high availability. Dynamic cache is implemented to improve application response times and reduce system load. In a clustered environment, each JVM (cluster member) has a cache instance that generates its unique cache content, in memory first with the option to offload excessive cache content to disk.
WebSphere Commerce runtime creates many cached objects in the background. Hence, data replication service is required in a clustered environment to ensure that these runtime cached objects are invalidated across the cluster.
When designing your cache strategy in this highly available environment, a few important questions must be answered:
- What options are available to ensure the consistency of cache content across a cluster?
- What are the pros and cons of each option?
- What does cache replication do?
- How does cache replication work?
- How much performance improvement does cache replication provide?
- What is the performance overhead of cache replication?
- How will you tune cache replication to reap the most benefit out of it and reduce the performance overhead?
- How will you configure cache replication?
- What does WebSphere Commerce recommend with respect to cache replication?